Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff5ffe55eb81e021add015d85a0d025e6566b1dec42d6d29f5a182f27704cf4b

Tx prefix hash: 84beb5ea9bbd5e49c71356fe84042953640f0d60caeba67735c37ef71768c1e3
Tx public key: 2cc67e5a1d442354bfb05c558091ff65721f7ba70f11d1844ffa9fb7a8f8a588
Timestamp: 1581243604 Timestamp [UCT]: 2020-02-09 10:20:04 Age [y:d:h:m:s]: 04:358:10:44:56
Block: 61212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148106 RingCT/type: yes/0
Extra: 012cc67e5a1d442354bfb05c558091ff65721f7ba70f11d1844ffa9fb7a8f8a588021100000198c71d3ff9000000000000000000

1 output(s) for total of 384.751259551000 dcy

stealth address amount amount idx
00: c26ce10e7197ae24383e6947730e10c2ca85c3ba9aa4b2c3eeb1277f9e578f84 384.751259551000 112801 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": 61222, "vin": [ { "gen": { "height": 61212 } } ], "vout": [ { "amount": 384751259551, "target": { "key": "c26ce10e7197ae24383e6947730e10c2ca85c3ba9aa4b2c3eeb1277f9e578f84" } } ], "extra": [ 1, 44, 198, 126, 90, 29, 68, 35, 84, 191, 176, 92, 85, 128, 145, 255, 101, 114, 31, 123, 167, 15, 17, 209, 132, 79, 250, 159, 183, 168, 248, 165, 136, 2, 17, 0, 0, 1, 152, 199, 29, 63, 249, 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