Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d73d086357bc6b8d414ead9b7fab8817f331fa9fa596e3c3deae577fa663a6b

Tx prefix hash: 7c1b07a2cbb38f85fc819db5a10308a5673c059bd5affb501d5c784d1e311b56
Tx public key: fbab8c4d34ab95d35674da6575b87c62b271fe80c9a625304737fcebb7510a06
Timestamp: 1704560195 Timestamp [UCT]: 2024-01-06 16:56:35 Age [y:d:h:m:s]: 01:308:07:30:00
Block: 929537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479183 RingCT/type: yes/0
Extra: 01fbab8c4d34ab95d35674da6575b87c62b271fe80c9a625304737fcebb7510a0602110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd177ecbf5091152681d98e16fcf36751701739e0d4a96b06e19a5cdc2b1fca0 0.600000000000 1387413 of 15

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": 929547, "vin": [ { "gen": { "height": 929537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd177ecbf5091152681d98e16fcf36751701739e0d4a96b06e19a5cdc2b1fca0" } } ], "extra": [ 1, 251, 171, 140, 77, 52, 171, 149, 211, 86, 116, 218, 101, 117, 184, 124, 98, 178, 113, 254, 128, 201, 166, 37, 48, 71, 55, 252, 235, 183, 81, 10, 6, 2, 17, 0, 0, 0, 6, 82, 212, 126, 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