Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2f7704e61d51b6e43b92ce3639605726e935f9c0d4bcf962b71e37255d22b97

Tx prefix hash: 007bd009ef73bb704415d6f3dc0017267c2e8e769a24fef3e550e82e8808ebca
Tx public key: b17356e24ad0f1f84d967ee334a5cbb18b47daa8b5fc06c88f78380a7d34d11c
Timestamp: 1715905594 Timestamp [UCT]: 2024-05-17 00:26:34 Age [y:d:h:m:s]: 00:348:11:17:32
Block: 1023612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249104 RingCT/type: yes/0
Extra: 01b17356e24ad0f1f84d967ee334a5cbb18b47daa8b5fc06c88f78380a7d34d11c02110000001559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3be85a9a3bab44a071f275f1e49720844be49a2e107a7ebf0027c4a7177fbf88 0.600000000000 1488717 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": 1023622, "vin": [ { "gen": { "height": 1023612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3be85a9a3bab44a071f275f1e49720844be49a2e107a7ebf0027c4a7177fbf88" } } ], "extra": [ 1, 177, 115, 86, 226, 74, 208, 241, 248, 77, 150, 126, 227, 52, 165, 203, 177, 139, 71, 218, 168, 181, 252, 6, 200, 143, 120, 56, 10, 125, 52, 209, 28, 2, 17, 0, 0, 0, 21, 89, 218, 211, 245, 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