Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8970a8c98bc1e4c35fe050b4a91e1179797a452b3be2777ddda2cfba036d274

Tx prefix hash: ae633f456acaa75187dcf33853b13e481962bbd20bf69cb6ac0b58fd81b4486e
Tx public key: 3b95745d298f15b48e77dd888c63c0a6078646dc4adb7ab891fe8b4671c0a8cc
Timestamp: 1582383629 Timestamp [UCT]: 2020-02-22 15:00:29 Age [y:d:h:m:s]: 05:111:11:54:42
Block: 70239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232921 RingCT/type: yes/0
Extra: 013b95745d298f15b48e77dd888c63c0a6078646dc4adb7ab891fe8b4671c0a8cc02110000000112c4732d000000000000000000

1 output(s) for total of 359.151211701000 dcy

stealth address amount amount idx
00: 9cc5a7a858c3188855eb8978fe4d9e0b51ea256ccfc645b6b942f083ccc91134 359.151211701000 129712 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": 70249, "vin": [ { "gen": { "height": 70239 } } ], "vout": [ { "amount": 359151211701, "target": { "key": "9cc5a7a858c3188855eb8978fe4d9e0b51ea256ccfc645b6b942f083ccc91134" } } ], "extra": [ 1, 59, 149, 116, 93, 41, 143, 21, 180, 142, 119, 221, 136, 140, 99, 192, 166, 7, 134, 70, 220, 74, 219, 122, 184, 145, 254, 139, 70, 113, 192, 168, 204, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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