Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6c4f378083c47cf2f414ecd50c879e18c21b9afc6adc2df20fa57c2cd79b25

Tx prefix hash: 658a406e7eb7dfab0767f5719f4867e999ccf370575e1ac3f653ef242bd2ec60
Tx public key: f10e508bcfe3a8dc291f572f2c9ecef528826541add2f1db21d75f6f72880d2f
Timestamp: 1759657361 Timestamp [UCT]: 2025-10-05 09:42:41 Age [y:d:h:m:s]: 00:091:16:10:43
Block: 1383217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65650 RingCT/type: yes/0
Extra: 01f10e508bcfe3a8dc291f572f2c9ecef528826541add2f1db21d75f6f72880d2f021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecd96e5e7eec05484961953de2ea5dbdb36d40797531980c63697da23447dea1 0.600000000000 1871362 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": 1383227, "vin": [ { "gen": { "height": 1383217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecd96e5e7eec05484961953de2ea5dbdb36d40797531980c63697da23447dea1" } } ], "extra": [ 1, 241, 14, 80, 139, 207, 227, 168, 220, 41, 31, 87, 47, 44, 158, 206, 245, 40, 130, 101, 65, 173, 210, 241, 219, 33, 215, 95, 111, 114, 136, 13, 47, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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