Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233db908ea509b672c5ecd601da90a234d4381921e7b80c06b8188a388a008a7

Tx prefix hash: 072d25e1cd0e5872032e72b3afa8574c00f7661357aa22d2ca5136cd84f3725e
Tx public key: 3894c1cf95dda2b958e3600a9ba54de8dad56f9d546c7127a69e4a1edcfbce40
Timestamp: 1577797802 Timestamp [UCT]: 2019-12-31 13:10:02 Age [y:d:h:m:s]: 05:035:11:49:56
Block: 35758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175103 RingCT/type: yes/0
Extra: 013894c1cf95dda2b958e3600a9ba54de8dad56f9d546c7127a69e4a1edcfbce40021100000036398c17aa000000000000000000

1 output(s) for total of 467.218204381000 dcy

stealth address amount amount idx
00: 7f51c2c268d05154ba00543392828e7ad608e4cf871d1d8eeaea7b332211c4f6 467.218204381000 60384 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": 35768, "vin": [ { "gen": { "height": 35758 } } ], "vout": [ { "amount": 467218204381, "target": { "key": "7f51c2c268d05154ba00543392828e7ad608e4cf871d1d8eeaea7b332211c4f6" } } ], "extra": [ 1, 56, 148, 193, 207, 149, 221, 162, 185, 88, 227, 96, 10, 155, 165, 77, 232, 218, 213, 111, 157, 84, 108, 113, 39, 166, 158, 74, 30, 220, 251, 206, 64, 2, 17, 0, 0, 0, 54, 57, 140, 23, 170, 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