Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426eff325ddb84d81fe69abed77ce4e504f489a849e0f2871cb73cf98a4234a7

Tx prefix hash: 7518921306380606a3d9be8c1d2bc6a582bf25eda9d8b140f8f2f7ebd30b6b8b
Tx public key: d4d03965dc034b9637a5bdb9c6918675fef8d45ddcc74863c5e37aefa6d86738
Timestamp: 1736852316 Timestamp [UCT]: 2025-01-14 10:58:36 Age [y:d:h:m:s]: 00:155:01:33:18
Block: 1197122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110535 RingCT/type: yes/0
Extra: 01d4d03965dc034b9637a5bdb9c6918675fef8d45ddcc74863c5e37aefa6d867380211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b6ab0d3574d263b201120c7e9221b95ed3b1d58e76ae02c588474a282b5879d 0.600000000000 1683727 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": 1197132, "vin": [ { "gen": { "height": 1197122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b6ab0d3574d263b201120c7e9221b95ed3b1d58e76ae02c588474a282b5879d" } } ], "extra": [ 1, 212, 208, 57, 101, 220, 3, 75, 150, 55, 165, 189, 185, 198, 145, 134, 117, 254, 248, 212, 93, 220, 199, 72, 99, 197, 227, 122, 239, 166, 216, 103, 56, 2, 17, 0, 0, 0, 1, 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