Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d2465645007e08a0bc332fe7abade9efbb2779ad411f0786a0864901afd3760

Tx prefix hash: 297648f942a4a4a571fbdf1b4a85c4b64b7f58eceef4ca6de1c181defafdc767
Tx public key: 7cfdcddaf1d970214e499acfa176d5f0602bbdf323067d5e61750c3a4392bdae
Timestamp: 1703321713 Timestamp [UCT]: 2023-12-23 08:55:13 Age [y:d:h:m:s]: 02:038:17:24:41
Block: 919282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547315 RingCT/type: yes/0
Extra: 017cfdcddaf1d970214e499acfa176d5f0602bbdf323067d5e61750c3a4392bdae02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6184fa3dc149b0b25b6e50fb2803f6159c4f3774f381c8e3727aa87c9cb8f174 0.600000000000 1376948 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": 919292, "vin": [ { "gen": { "height": 919282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6184fa3dc149b0b25b6e50fb2803f6159c4f3774f381c8e3727aa87c9cb8f174" } } ], "extra": [ 1, 124, 253, 205, 218, 241, 217, 112, 33, 78, 73, 154, 207, 161, 118, 213, 240, 96, 43, 189, 243, 35, 6, 125, 94, 97, 117, 12, 58, 67, 146, 189, 174, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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