Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2efc3821a33e9c7956e8aa09d62e3d0f6b6f0131f75f409d609791033edda7b7

Tx prefix hash: 21f58c550c5e8248b17b568c073f937074b52da43b237c300a43eced500d62ff
Tx public key: fc2cdbd0236d9a508bcef3258dca3cefb21dfbc35cfaf6410be170b112c87a51
Timestamp: 1714405041 Timestamp [UCT]: 2024-04-29 15:37:21 Age [y:d:h:m:s]: 01:029:21:27:12
Block: 1011170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282333 RingCT/type: yes/0
Extra: 01fc2cdbd0236d9a508bcef3258dca3cefb21dfbc35cfaf6410be170b112c87a510211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f89e450cbae6a2b712079658eaef39a1b48c09b5d740dcc2ad20b9d41dd004e 0.600000000000 1473330 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": 1011180, "vin": [ { "gen": { "height": 1011170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f89e450cbae6a2b712079658eaef39a1b48c09b5d740dcc2ad20b9d41dd004e" } } ], "extra": [ 1, 252, 44, 219, 208, 35, 109, 154, 80, 139, 206, 243, 37, 141, 202, 60, 239, 178, 29, 251, 195, 92, 250, 246, 65, 11, 225, 112, 177, 18, 200, 122, 81, 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