Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0cbf80b1434046610d8ababa4eba6c1f1b0920ab880b37087009acbd6ad995e

Tx prefix hash: 46347630090b7d6222d8c119ef322db79f4dc464c3e6865a5acc3409af22d212
Tx public key: fb33ec1f8de929cc7e8c40e178fe73cef0d126ed7b9b32d0d425a5ae103e062b
Timestamp: 1741435548 Timestamp [UCT]: 2025-03-08 12:05:48 Age [y:d:h:m:s]: 00:060:17:51:17
Block: 1234815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43434 RingCT/type: yes/0
Extra: 01fb33ec1f8de929cc7e8c40e178fe73cef0d126ed7b9b32d0d425a5ae103e062b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35765bed29dd94dd99bf96e214cdb2622c96aaf76e77b5e5ec95bcbec5fdc41b 0.600000000000 1721750 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": 1234825, "vin": [ { "gen": { "height": 1234815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35765bed29dd94dd99bf96e214cdb2622c96aaf76e77b5e5ec95bcbec5fdc41b" } } ], "extra": [ 1, 251, 51, 236, 31, 141, 233, 41, 204, 126, 140, 64, 225, 120, 254, 115, 206, 240, 209, 38, 237, 123, 155, 50, 208, 212, 37, 165, 174, 16, 62, 6, 43, 2, 17, 0, 0, 0, 6, 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