Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 01369a493e2e08c39ea749784d965fc2c91161f9feb055ea7a6440092354fce5

Tx prefix hash: 029a76c17c91f7743c86ecfa124771675d58d9d660bcf54dc59ae0abd881a07e
Tx public key: e941a907d3d5ccd38acdc08d2e16ca5be1f67a425f682ef56906d4cb06fb46f7
Timestamp: 1658839837 Timestamp [UCT]: 2022-07-26 12:50:37 Age [y:d:h:m:s]: 02:162:12:33:01
Block: 552134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 637557 RingCT/type: yes/0
Extra: 01e941a907d3d5ccd38acdc08d2e16ca5be1f67a425f682ef56906d4cb06fb46f702110000000133af99f4000000000000000000

1 output(s) for total of 9.089730047000 dcy

stealth address amount amount idx
00: 2baa4442eeede2bccd674015303181cbb0a2145fe6b69052d7255e875322b268 9.089730047000 983802 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 552144, "vin": [ { "gen": { "height": 552134 } } ], "vout": [ { "amount": 9089730047, "target": { "key": "2baa4442eeede2bccd674015303181cbb0a2145fe6b69052d7255e875322b268" } } ], "extra": [ 1, 233, 65, 169, 7, 211, 213, 204, 211, 138, 205, 192, 141, 46, 22, 202, 91, 225, 246, 122, 66, 95, 104, 46, 245, 105, 6, 212, 203, 6, 251, 70, 247, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8