Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6a5aa568943716125edf23dfb32ef41912c8cde5e493f714dee65071f470523

Tx prefix hash: bcd7c4c51460f902168b6a73d8094fe4c75d465fd6772728f6d4a1173e30219d
Tx public key: ef2f4f6d2edc84f03ddf0a532e3e3de3390eb550e5d6ec8934ec4df0f7ee052b
Timestamp: 1705270136 Timestamp [UCT]: 2024-01-14 22:08:56 Age [y:d:h:m:s]: 01:063:00:30:21
Block: 935421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306147 RingCT/type: yes/0
Extra: 01ef2f4f6d2edc84f03ddf0a532e3e3de3390eb550e5d6ec8934ec4df0f7ee052b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba1b986d7a08ed135e76730ae395bbb14f7dcde77378a92e4bfa0d811fbb1c81 0.600000000000 1393437 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": 935431, "vin": [ { "gen": { "height": 935421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba1b986d7a08ed135e76730ae395bbb14f7dcde77378a92e4bfa0d811fbb1c81" } } ], "extra": [ 1, 239, 47, 79, 109, 46, 220, 132, 240, 61, 223, 10, 83, 46, 62, 61, 227, 57, 14, 181, 80, 229, 214, 236, 137, 52, 236, 77, 240, 247, 238, 5, 43, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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