Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4e7a2c3870f37e20cc39c6579970f9f08ed1af644b56c99c45b754b743edc9

Tx prefix hash: 50c362eed1bb7b084ec708bebf47b13dcf35e630596034ec5ea71b91ae684418
Tx public key: 43db76bef006d9e87acb1f89d3cdea7d41a8bb1f59db9b2c872ddc775a34ae11
Timestamp: 1764269794 Timestamp [UCT]: 2025-11-27 18:56:34 Age [y:d:h:m:s]: 00:026:00:39:13
Block: 1421455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18614 RingCT/type: yes/0
Extra: 0143db76bef006d9e87acb1f89d3cdea7d41a8bb1f59db9b2c872ddc775a34ae11021100000004fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fdc8e645d70cf90fc8394c4c36dcd671e83c1d3a42eec8f49b02fa2d00d5e14 0.600000000000 1910012 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": 1421465, "vin": [ { "gen": { "height": 1421455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fdc8e645d70cf90fc8394c4c36dcd671e83c1d3a42eec8f49b02fa2d00d5e14" } } ], "extra": [ 1, 67, 219, 118, 190, 240, 6, 217, 232, 122, 203, 31, 137, 211, 205, 234, 125, 65, 168, 187, 31, 89, 219, 155, 44, 135, 45, 220, 119, 90, 52, 174, 17, 2, 17, 0, 0, 0, 4, 251, 143, 208, 137, 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