Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b13958b8d43b6dfebe7f17ed0d6c6ff58bd97640f7ab463be9485cfeb48c4c92

Tx prefix hash: 5d9743bdbcb5a37b4b65e9f66af0aef88375c55685697a15993378bd055e592f
Tx public key: 8ea1b49097b41ccead283ebc0d5f6d36d462350cfeea0ff3ffd8797fb4389ccb
Timestamp: 1756164522 Timestamp [UCT]: 2025-08-25 23:28:42 Age [y:d:h:m:s]: 00:136:15:47:19
Block: 1354451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97675 RingCT/type: yes/0
Extra: 018ea1b49097b41ccead283ebc0d5f6d36d462350cfeea0ff3ffd8797fb4389ccb021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59d99f003463cfeb00ac8c92bb4dfa3f0b8b3b6f54ab0c3c7458d3217abee0a8 0.600000000000 1842440 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": 1354461, "vin": [ { "gen": { "height": 1354451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59d99f003463cfeb00ac8c92bb4dfa3f0b8b3b6f54ab0c3c7458d3217abee0a8" } } ], "extra": [ 1, 142, 161, 180, 144, 151, 180, 28, 206, 173, 40, 62, 188, 13, 95, 109, 54, 212, 98, 53, 12, 254, 234, 15, 243, 255, 216, 121, 127, 180, 56, 156, 203, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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