Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b84f0e21b727b489605c447415bfe8bcd191155fd6bed74d2a7eb57e92452b95

Tx prefix hash: bb912e7564a9f4a138d1dc66fba4dee34e9d6307fa45ab7ade6a8460efb7ff59
Tx public key: f93aa87abda5168a1d52ad5b4ef819f76f52e782240fa6c7671d0ddfc0857aa2
Timestamp: 1743367855 Timestamp [UCT]: 2025-03-30 20:50:55 Age [y:d:h:m:s]: 00:282:15:22:03
Block: 1250795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199812 RingCT/type: yes/0
Extra: 01f93aa87abda5168a1d52ad5b4ef819f76f52e782240fa6c7671d0ddfc0857aa20211000000011a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd4d04d7c1acebb525b8613c513d7bcbc56159b3857a6ec3745778b8bb210d73 0.600000000000 1737848 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": 1250805, "vin": [ { "gen": { "height": 1250795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd4d04d7c1acebb525b8613c513d7bcbc56159b3857a6ec3745778b8bb210d73" } } ], "extra": [ 1, 249, 58, 168, 122, 189, 165, 22, 138, 29, 82, 173, 91, 78, 248, 25, 247, 111, 82, 231, 130, 36, 15, 166, 199, 103, 29, 13, 223, 192, 133, 122, 162, 2, 17, 0, 0, 0, 1, 26, 151, 4, 3, 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