Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d270b8ec35a55dcd4a2a4766eeefa5104dac24e3c8facf4825227b276d5c5910

Tx prefix hash: 0af671d64aa83822592c8e9f3b1b27ea95d22cd6c294f06dd102f54a649bf653
Tx public key: 1740bf75a5ab1825b69cde3c37ad34f35a5a1a0b696a95ddb283930f23822143
Timestamp: 1706427456 Timestamp [UCT]: 2024-01-28 07:37:36 Age [y:d:h:m:s]: 01:101:15:47:47
Block: 945009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333754 RingCT/type: yes/0
Extra: 011740bf75a5ab1825b69cde3c37ad34f35a5a1a0b696a95ddb283930f238221430211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee8ecbbce6c652cb30481d6378a9a430e57407827af7c97dd361a6aba009e1c9 0.600000000000 1403317 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": 945019, "vin": [ { "gen": { "height": 945009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee8ecbbce6c652cb30481d6378a9a430e57407827af7c97dd361a6aba009e1c9" } } ], "extra": [ 1, 23, 64, 191, 117, 165, 171, 24, 37, 182, 156, 222, 60, 55, 173, 52, 243, 90, 90, 26, 11, 105, 106, 149, 221, 178, 131, 147, 15, 35, 130, 33, 67, 2, 17, 0, 0, 0, 2, 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