Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bba7a9b77d8f997bcbbe202711204b742b9033dbf664b425e2f8e8b7a3def94

Tx prefix hash: 09db3d55706661ed92b4bd1508e9d5a857077cd5c0dfaa132d0746708e52aa31
Tx public key: 660f2fd8a13ea13a1da4090250cf09a70956b58e6e73985aefd0af25849cf664
Timestamp: 1732725344 Timestamp [UCT]: 2024-11-27 16:35:44 Age [y:d:h:m:s]: 01:006:20:58:55
Block: 1162951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263364 RingCT/type: yes/0
Extra: 01660f2fd8a13ea13a1da4090250cf09a70956b58e6e73985aefd0af25849cf664021100000006d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 365b162613d3fc97d5a0d4c9c9e90964af9d152ae2f54f9629a9db5b0646f726 0.600000000000 1648614 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": 1162961, "vin": [ { "gen": { "height": 1162951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "365b162613d3fc97d5a0d4c9c9e90964af9d152ae2f54f9629a9db5b0646f726" } } ], "extra": [ 1, 102, 15, 47, 216, 161, 62, 161, 58, 29, 164, 9, 2, 80, 207, 9, 167, 9, 86, 181, 142, 110, 115, 152, 90, 239, 208, 175, 37, 132, 156, 246, 100, 2, 17, 0, 0, 0, 6, 216, 231, 210, 65, 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