Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1a43a183e837310991cfe0d0ef014a22d1e0cec4ab8928adea38db148940840

Tx prefix hash: 0b73ad2ff7b9f51583155a3a7fcdd3973ce368f90da561d44508e285eed5bbae
Tx public key: 4858f24364f5e98672c0af3a885d12ace53ee28e62d72d6e743b2c35c418fd11
Timestamp: 1710250545 Timestamp [UCT]: 2024-03-12 13:35:45 Age [y:d:h:m:s]: 01:063:20:09:21
Block: 976739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306632 RingCT/type: yes/0
Extra: 014858f24364f5e98672c0af3a885d12ace53ee28e62d72d6e743b2c35c418fd1102110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aaf46da6982039336a1b1b91a61ad396770b2a0418f035cc09802f82e59b1be 0.600000000000 1436734 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": 976749, "vin": [ { "gen": { "height": 976739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aaf46da6982039336a1b1b91a61ad396770b2a0418f035cc09802f82e59b1be" } } ], "extra": [ 1, 72, 88, 242, 67, 100, 245, 233, 134, 114, 192, 175, 58, 136, 93, 18, 172, 229, 62, 226, 142, 98, 215, 45, 110, 116, 59, 44, 53, 196, 24, 253, 17, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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