Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a6aa449a55f77cab477748c4fec9c619601fc891c53d08338914e8cd99d0ea

Tx prefix hash: 278dee816c40beac36ac0657a51e4856113c6e49bd78e44c7ce119482ba978fe
Tx public key: bdce6fa2e1e904ab701cb63802e9f2499a274e31ab708e70afff3732c7957c0a
Timestamp: 1675026912 Timestamp [UCT]: 2023-01-29 21:15:12 Age [y:d:h:m:s]: 02:028:00:02:50
Block: 685596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541608 RingCT/type: yes/0
Extra: 01bdce6fa2e1e904ab701cb63802e9f2499a274e31ab708e70afff3732c7957c0a021100000003835e4d22000000000000000000

1 output(s) for total of 3.283490635000 dcy

stealth address amount amount idx
00: a3491be79791f946c559c404618bb0ce60097d3a25ab22a5ab37c3c76ae8e92b 3.283490635000 1127947 of 0

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": 685606, "vin": [ { "gen": { "height": 685596 } } ], "vout": [ { "amount": 3283490635, "target": { "key": "a3491be79791f946c559c404618bb0ce60097d3a25ab22a5ab37c3c76ae8e92b" } } ], "extra": [ 1, 189, 206, 111, 162, 225, 233, 4, 171, 112, 28, 182, 56, 2, 233, 242, 73, 154, 39, 78, 49, 171, 112, 142, 112, 175, 255, 55, 50, 199, 149, 124, 10, 2, 17, 0, 0, 0, 3, 131, 94, 77, 34, 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