Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c7be266104063579951b2c29a5b749a9a093d8a848751ebda6d4675b6d6145c

Tx prefix hash: c89471b3bbfb0a3950cd2afb2c974e7af7651ad4fb6314d6e1cc68c9d879a397
Tx public key: ff7afcbd47dfc061f62bb9d659c48a0954c83a0b365c55b1cea98c0aff074de0
Timestamp: 1737538780 Timestamp [UCT]: 2025-01-22 09:39:40 Age [y:d:h:m:s]: 00:148:03:36:42
Block: 1202767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105618 RingCT/type: yes/0
Extra: 01ff7afcbd47dfc061f62bb9d659c48a0954c83a0b365c55b1cea98c0aff074de0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1063ddc1b1e3982ea906e4feb16a41961777c5319e533834ee5759ee5c9998c8 0.600000000000 1689434 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": 1202777, "vin": [ { "gen": { "height": 1202767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1063ddc1b1e3982ea906e4feb16a41961777c5319e533834ee5759ee5c9998c8" } } ], "extra": [ 1, 255, 122, 252, 189, 71, 223, 192, 97, 246, 43, 185, 214, 89, 196, 138, 9, 84, 200, 58, 11, 54, 92, 85, 177, 206, 169, 140, 10, 255, 7, 77, 224, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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