Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 553ca07f556227f3aa299f8e5038e38ea7fc07198dc42518ed578445339fccef

Tx prefix hash: eab1e4973e456a692fd08ed58406c77113376774bc2db5f545d124f7bf29646a
Tx public key: a1dda54200d6770716f41e0f7d0d9079e0f5ea1695f00ab295c78f645b150d40
Timestamp: 1648589364 Timestamp [UCT]: 2022-03-29 21:29:24 Age [y:d:h:m:s]: 03:226:05:20:25
Block: 469156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 939636 RingCT/type: yes/0
Extra: 01a1dda54200d6770716f41e0f7d0d9079e0f5ea1695f00ab295c78f645b150d4002110000001906faf294000000000000000000

1 output(s) for total of 17.119523275000 dcy

stealth address amount amount idx
00: e492d5900235a29c01bb6b24a2092f7f6f6ed38b137d23a9e100ed8026d64d0a 17.119523275000 888044 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": 469166, "vin": [ { "gen": { "height": 469156 } } ], "vout": [ { "amount": 17119523275, "target": { "key": "e492d5900235a29c01bb6b24a2092f7f6f6ed38b137d23a9e100ed8026d64d0a" } } ], "extra": [ 1, 161, 221, 165, 66, 0, 214, 119, 7, 22, 244, 30, 15, 125, 13, 144, 121, 224, 245, 234, 22, 149, 240, 10, 178, 149, 199, 143, 100, 91, 21, 13, 64, 2, 17, 0, 0, 0, 25, 6, 250, 242, 148, 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