Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52cfb366f906020295a19405aee348dcfd34f5961a316b1c398f672035acd494

Tx prefix hash: 401a5e28311a15ed98fd0126d287714ce2d0d917de0c69249ab6ba381273fbf9
Tx public key: de6c6d3f4d29a213d6493abd49fed085450b30bfc8c361618f05eccc5393400a
Timestamp: 1574566228 Timestamp [UCT]: 2019-11-24 03:30:28 Age [y:d:h:m:s]: 05:101:19:02:29
Block: 16130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1215401 RingCT/type: yes/0
Extra: 01de6c6d3f4d29a213d6493abd49fed085450b30bfc8c361618f05eccc5393400a021100000008f95225a5000000000000000000

1 output(s) for total of 542.694595499000 dcy

stealth address amount amount idx
00: 0d51416cb31fa0e5359c07583734b78f4c6a3dde22f679e8c16137eff48b5a98 542.694595499000 22332 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": 16140, "vin": [ { "gen": { "height": 16130 } } ], "vout": [ { "amount": 542694595499, "target": { "key": "0d51416cb31fa0e5359c07583734b78f4c6a3dde22f679e8c16137eff48b5a98" } } ], "extra": [ 1, 222, 108, 109, 63, 77, 41, 162, 19, 214, 73, 58, 189, 73, 254, 208, 133, 69, 11, 48, 191, 200, 195, 97, 97, 143, 5, 236, 204, 83, 147, 64, 10, 2, 17, 0, 0, 0, 8, 249, 82, 37, 165, 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