Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 213ac75b297180be4ac9170e6d3f9ceb50529d23ad65e783385e5880fb20e3e9

Tx prefix hash: a1172fa0b2d1fdb8392743826738052a2934dd2759e0ba263f91d4e6233fe76b
Tx public key: 0c058ef46e2b5a8a38261371cde159d4dd9f6bc04a41aa81daba37b09656b843
Timestamp: 1717976746 Timestamp [UCT]: 2024-06-09 23:45:46 Age [y:d:h:m:s]: 00:143:13:42:18
Block: 1040774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102778 RingCT/type: yes/0
Extra: 010c058ef46e2b5a8a38261371cde159d4dd9f6bc04a41aa81daba37b09656b8430211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eaf577e631c018521743e9e1e7e5e8f530b20154df3ff38a0ed9185b84abf80 0.600000000000 1509437 of 15

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": 1040784, "vin": [ { "gen": { "height": 1040774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eaf577e631c018521743e9e1e7e5e8f530b20154df3ff38a0ed9185b84abf80" } } ], "extra": [ 1, 12, 5, 142, 244, 110, 43, 90, 138, 56, 38, 19, 113, 205, 225, 89, 212, 221, 159, 107, 192, 74, 65, 170, 129, 218, 186, 55, 176, 150, 86, 184, 67, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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