Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a4b527a1a5a18f3016b244ffe3371bee448fc42df1ba40499d1b2588c8002d

Tx prefix hash: 2659bc14c9d577060a659bf950e10622fdadf2cf7ccf4910ca6ada1a0430e603
Tx public key: 0a219a819f66195197c38efcf8465435cdde35bbcee2c5385a24a4e37a95ea76
Timestamp: 1655855584 Timestamp [UCT]: 2022-06-21 23:53:04 Age [y:d:h:m:s]: 03:132:22:03:43
Block: 527545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 874660 RingCT/type: yes/0
Extra: 010a219a819f66195197c38efcf8465435cdde35bbcee2c5385a24a4e37a95ea76021100000002faf35c9c000000000000000000

1 output(s) for total of 10.965402706000 dcy

stealth address amount amount idx
00: 767e124f2f9ec81683a0e4ff7fba5bce3302f45dda1d63883bd2e8b8f3df7688 10.965402706000 956234 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": 527555, "vin": [ { "gen": { "height": 527545 } } ], "vout": [ { "amount": 10965402706, "target": { "key": "767e124f2f9ec81683a0e4ff7fba5bce3302f45dda1d63883bd2e8b8f3df7688" } } ], "extra": [ 1, 10, 33, 154, 129, 159, 102, 25, 81, 151, 195, 142, 252, 248, 70, 84, 53, 205, 222, 53, 187, 206, 226, 197, 56, 90, 36, 164, 227, 122, 149, 234, 118, 2, 17, 0, 0, 0, 2, 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