Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7389dcb4bb20d6941516d578f8409b782f9c44760bada8301dc0e7db74b30ed0

Tx prefix hash: 1516423e6da283936ec231e3d1e0a4450f26dbcfc4c02a98771a18dd2c654b38
Tx public key: 7834345b968216ee7aac1a55d72e41f66c4741900681ae77d0f921eda8d0848e
Timestamp: 1577556679 Timestamp [UCT]: 2019-12-28 18:11:19 Age [y:d:h:m:s]: 05:001:20:05:23
Block: 33687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151368 RingCT/type: yes/0
Extra: 017834345b968216ee7aac1a55d72e41f66c4741900681ae77d0f921eda8d0848e02110000002d398c17aa000000000000000000

1 output(s) for total of 474.659133128000 dcy

stealth address amount amount idx
00: fd53aae4883cfd18e1c2d212137d5bf94921caa64a0899fb7670600fd0392461 474.659133128000 56499 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": 33697, "vin": [ { "gen": { "height": 33687 } } ], "vout": [ { "amount": 474659133128, "target": { "key": "fd53aae4883cfd18e1c2d212137d5bf94921caa64a0899fb7670600fd0392461" } } ], "extra": [ 1, 120, 52, 52, 91, 150, 130, 22, 238, 122, 172, 26, 85, 215, 46, 65, 246, 108, 71, 65, 144, 6, 129, 174, 119, 208, 249, 33, 237, 168, 208, 132, 142, 2, 17, 0, 0, 0, 45, 57, 140, 23, 170, 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