Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcba1e9fb06f2a73658bb588d4e3529d5389cff9f75af552e16f764c00b3d126

Tx prefix hash: 866dc8ff815da050bc2bec26d0d10cecb37d4b0cd145d26363c3d262161a47f3
Tx public key: 53083d295102ccfc86035b0a445c01b73dc200fb15a6fe8739e0f6ce7995e9cf
Timestamp: 1608190161 Timestamp [UCT]: 2020-12-17 07:29:21 Age [y:d:h:m:s]: 04:050:10:22:22
Block: 163692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1048393 RingCT/type: yes/0
Extra: 0153083d295102ccfc86035b0a445c01b73dc200fb15a6fe8739e0f6ce7995e9cf0211000015824ea414e5000000000000000000

1 output(s) for total of 176.055169214000 dcy

stealth address amount amount idx
00: 073f2a9aea338480b4c96f02fb2e7aed8b62c699c2bde5568e6df7e74cb31e7d 176.055169214000 294223 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": 163702, "vin": [ { "gen": { "height": 163692 } } ], "vout": [ { "amount": 176055169214, "target": { "key": "073f2a9aea338480b4c96f02fb2e7aed8b62c699c2bde5568e6df7e74cb31e7d" } } ], "extra": [ 1, 83, 8, 61, 41, 81, 2, 204, 252, 134, 3, 91, 10, 68, 92, 1, 183, 61, 194, 0, 251, 21, 166, 254, 135, 57, 224, 246, 206, 121, 149, 233, 207, 2, 17, 0, 0, 21, 130, 78, 164, 20, 229, 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