Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8902a9a28aa9e59905355dcc0f3c280d3ba0e6ea651114b55243864def6166a

Tx prefix hash: a301ddaa980286bb1e0d27483f5ae993b282e2cf8163d18f8655133eaf9c2cd3
Tx public key: e8bbb1e87685c8a30f805780f798887e6e72f3eb88c42d2a36ab109b80098af1
Timestamp: 1698829146 Timestamp [UCT]: 2023-11-01 08:59:06 Age [y:d:h:m:s]: 01:229:10:37:11
Block: 882244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424907 RingCT/type: yes/0
Extra: 01e8bbb1e87685c8a30f805780f798887e6e72f3eb88c42d2a36ab109b80098af1021100000005faf35c9c000000000000000000

1 output(s) for total of 0.732418660000 dcy

stealth address amount amount idx
00: a53f656c60e52f67eac1c2bdfbf133fc787a3ba27f18216e6f14d78705d3b28e 0.732418660000 1337894 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": 882254, "vin": [ { "gen": { "height": 882244 } } ], "vout": [ { "amount": 732418660, "target": { "key": "a53f656c60e52f67eac1c2bdfbf133fc787a3ba27f18216e6f14d78705d3b28e" } } ], "extra": [ 1, 232, 187, 177, 232, 118, 133, 200, 163, 15, 128, 87, 128, 247, 152, 136, 126, 110, 114, 243, 235, 136, 196, 45, 42, 54, 171, 16, 155, 128, 9, 138, 241, 2, 17, 0, 0, 0, 5, 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