Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b41eded079437366c96e5c0e7e95fd80b3c9616b384522cf769da1c7eccdad5

Tx prefix hash: c30c4e98886a6a88ac6c78cd40e6bab6292d62be9e4bddfb8709f43a28b7dcc5
Tx public key: 264707e7cb0ff8bd05556513d15e0f770427590d23d0a1e9a5ae0585814eb129
Timestamp: 1735270337 Timestamp [UCT]: 2024-12-27 03:32:17 Age [y:d:h:m:s]: 00:100:17:06:14
Block: 1184026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71759 RingCT/type: yes/0
Extra: 01264707e7cb0ff8bd05556513d15e0f770427590d23d0a1e9a5ae0585814eb1290211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a2568f8f792ba242e0cc77bb7880ec5d26694e8477d892d68758d0c18683814 0.600000000000 1670479 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": 1184036, "vin": [ { "gen": { "height": 1184026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a2568f8f792ba242e0cc77bb7880ec5d26694e8477d892d68758d0c18683814" } } ], "extra": [ 1, 38, 71, 7, 231, 203, 15, 248, 189, 5, 85, 101, 19, 209, 94, 15, 119, 4, 39, 89, 13, 35, 208, 161, 233, 165, 174, 5, 133, 129, 78, 177, 41, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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