Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d5c87e152e461c500a4527b4a5980d28d55ee1d1032cffd10b9599aa11eecd7

Tx prefix hash: aa626a637a01038f34b56ff71b24500f17e7ef0bb0aa50ebec19b082830675f3
Tx public key: 800066473d2adce3b3c4232c3b9b70a72b8031098e2c6f249a1d63ac5495e491
Timestamp: 1705753936 Timestamp [UCT]: 2024-01-20 12:32:16 Age [y:d:h:m:s]: 01:095:16:19:48
Block: 939411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329508 RingCT/type: yes/0
Extra: 01800066473d2adce3b3c4232c3b9b70a72b8031098e2c6f249a1d63ac5495e49102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61c63b49a9d8ee52b16ce1402e4058e875e52992d77238dcf4b8478a742fa85f 0.600000000000 1397519 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": 939421, "vin": [ { "gen": { "height": 939411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61c63b49a9d8ee52b16ce1402e4058e875e52992d77238dcf4b8478a742fa85f" } } ], "extra": [ 1, 128, 0, 102, 71, 61, 42, 220, 227, 179, 196, 35, 44, 59, 155, 112, 167, 43, 128, 49, 9, 142, 44, 111, 36, 154, 29, 99, 172, 84, 149, 228, 145, 2, 17, 0, 0, 0, 2, 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