Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd0bc23e884bbaab9a9ed3b1cf3a79ae39b88a869237b0efd55591da4bcbcfcd

Tx prefix hash: 8185e0181f2c25dd2b7cd3c9223637da2d200dc53974e2bce38bfdab47e704b2
Tx public key: 808fd4e5918909e7ba722915fa5ef3c05f1f0eceb7e0e9b7e051d5b924d0468f
Timestamp: 1583537069 Timestamp [UCT]: 2020-03-06 23:24:29 Age [y:d:h:m:s]: 04:296:13:08:03
Block: 77780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106504 RingCT/type: yes/0
Extra: 01808fd4e5918909e7ba722915fa5ef3c05f1f0eceb7e0e9b7e051d5b924d0468f021100000001e89b4e54000000000000000000

1 output(s) for total of 339.065314759000 dcy

stealth address amount amount idx
00: fb6c868a039f53d27a85d671e985ac25e89466edc616ea920f40dec66ebd04e8 339.065314759000 142981 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": 77790, "vin": [ { "gen": { "height": 77780 } } ], "vout": [ { "amount": 339065314759, "target": { "key": "fb6c868a039f53d27a85d671e985ac25e89466edc616ea920f40dec66ebd04e8" } } ], "extra": [ 1, 128, 143, 212, 229, 145, 137, 9, 231, 186, 114, 41, 21, 250, 94, 243, 192, 95, 31, 14, 206, 183, 224, 233, 183, 224, 81, 213, 185, 36, 208, 70, 143, 2, 17, 0, 0, 0, 1, 232, 155, 78, 84, 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