Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a415ee3f38994e2f64e691cbc273577788d6cdde6ebcbe1ccaac2421d5e3334e

Tx prefix hash: e7f3a8e92fd508ea79ec6c14d6100b56fae9f5c325106b3439910201d41751d7
Tx public key: 5de8a6a96b2eaca2b5a9f84fba7a3033f7aa5c0700972d2b1dac928542b037ef
Timestamp: 1673071304 Timestamp [UCT]: 2023-01-07 06:01:44 Age [y:d:h:m:s]: 01:330:03:59:53
Block: 669346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497002 RingCT/type: yes/0
Extra: 015de8a6a96b2eaca2b5a9f84fba7a3033f7aa5c0700972d2b1dac928542b037ef021100000001faf35c9c000000000000000000

1 output(s) for total of 3.716882237000 dcy

stealth address amount amount idx
00: 457921e7c9a25a532bd077d58a0cde345ace1e6745e51b94569848207df8fa66 3.716882237000 1110655 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": 669356, "vin": [ { "gen": { "height": 669346 } } ], "vout": [ { "amount": 3716882237, "target": { "key": "457921e7c9a25a532bd077d58a0cde345ace1e6745e51b94569848207df8fa66" } } ], "extra": [ 1, 93, 232, 166, 169, 107, 46, 172, 162, 181, 169, 248, 79, 186, 122, 48, 51, 247, 170, 92, 7, 0, 151, 45, 43, 29, 172, 146, 133, 66, 176, 55, 239, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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