Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cbf3b144795ace01a6a691c9d128c3464cbb10f4d67c3c08199fc87da05e0b1

Tx prefix hash: ca78b9b71c33c4981d6343e56144ee608d2dd4bf337ff3320d82c92f890ff4fd
Tx public key: 1c773beefb3c4bcff0545e13d3096426e6cb40a080bb26d427a62045e557f427
Timestamp: 1683511813 Timestamp [UCT]: 2023-05-08 02:10:13 Age [y:d:h:m:s]: 02:041:14:04:58
Block: 755304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551754 RingCT/type: yes/0
Extra: 011c773beefb3c4bcff0545e13d3096426e6cb40a080bb26d427a62045e557f427021100000002e7ace25d000000000000000000

1 output(s) for total of 1.929143357000 dcy

stealth address amount amount idx
00: 40792ab8da3fc2e22c95acdc26d74cb73672fa7a1b7d02a893a5bdc795844c78 1.929143357000 1203617 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": 755314, "vin": [ { "gen": { "height": 755304 } } ], "vout": [ { "amount": 1929143357, "target": { "key": "40792ab8da3fc2e22c95acdc26d74cb73672fa7a1b7d02a893a5bdc795844c78" } } ], "extra": [ 1, 28, 119, 59, 238, 251, 60, 75, 207, 240, 84, 94, 19, 211, 9, 100, 38, 230, 203, 64, 160, 128, 187, 38, 212, 39, 166, 32, 69, 229, 87, 244, 39, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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