Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d610edbf88cf800225a3e7f2b8b4fe662afa88055e17fa8d32665bb5239ee5ee

Tx prefix hash: 9290353f5e82c89b2f8d7d8434c2830dc8d8792334ecbcb6acf62df9b8be4abf
Tx public key: acd9ed14fff971acd3bcc799854df4f85e463e1920f0a28ce902d2a3bddf16cc
Timestamp: 1674254385 Timestamp [UCT]: 2023-01-20 22:39:45 Age [y:d:h:m:s]: 01:364:23:01:25
Block: 679171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521808 RingCT/type: yes/0
Extra: 01acd9ed14fff971acd3bcc799854df4f85e463e1920f0a28ce902d2a3bddf16cc0211000000025029cbac000000000000000000

1 output(s) for total of 3.448454368000 dcy

stealth address amount amount idx
00: d64c1a5cb1af824b97d95d0e57a18c10e14e3f685ef5dc0d65c08eeacde67286 3.448454368000 1121140 of 0

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": 679181, "vin": [ { "gen": { "height": 679171 } } ], "vout": [ { "amount": 3448454368, "target": { "key": "d64c1a5cb1af824b97d95d0e57a18c10e14e3f685ef5dc0d65c08eeacde67286" } } ], "extra": [ 1, 172, 217, 237, 20, 255, 249, 113, 172, 211, 188, 199, 153, 133, 77, 244, 248, 94, 70, 62, 25, 32, 240, 162, 140, 233, 2, 210, 163, 189, 223, 22, 204, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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