Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2fea8afc42f4c56fd246543af5dd10e3144b53e44a4b3af9c1b56eca51b300a

Tx prefix hash: 320d670da4b087e5df2d815cf00e3d40f9150ce44356f0d5f33a1848e1c22148
Tx public key: 911f7fb04925140cce5ab23b0beef12ae51540481293b1c4809f2ce8a0f53b35
Timestamp: 1643300804 Timestamp [UCT]: 2022-01-27 16:26:44 Age [y:d:h:m:s]: 03:278:04:59:54
Block: 426456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 975736 RingCT/type: yes/0
Extra: 01911f7fb04925140cce5ab23b0beef12ae51540481293b1c4809f2ce8a0f53b35021100000001c9993c7f000000000000000000

1 output(s) for total of 23.712347724000 dcy

stealth address amount amount idx
00: e885b09b551f94238c40b86833dc0a2337c6c9a6e5ff5abf9c5ba5cdbe5c6d48 23.712347724000 835289 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": 426466, "vin": [ { "gen": { "height": 426456 } } ], "vout": [ { "amount": 23712347724, "target": { "key": "e885b09b551f94238c40b86833dc0a2337c6c9a6e5ff5abf9c5ba5cdbe5c6d48" } } ], "extra": [ 1, 145, 31, 127, 176, 73, 37, 20, 12, 206, 90, 178, 59, 11, 238, 241, 42, 229, 21, 64, 72, 18, 147, 177, 196, 128, 159, 44, 232, 160, 245, 59, 53, 2, 17, 0, 0, 0, 1, 201, 153, 60, 127, 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