Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a490d0008d3742942266af1c9e188d1b85d7a594b42704cb6311dc1b758d0c9

Tx prefix hash: 390d7f36733772e6c9561dd48eeae1e2a502c03e2c52c49da5b1721c1b3f1c07
Tx public key: e4adb511f4e23773811307db2a5660c07ed709c88d7ddcbee5c04a65130f347b
Timestamp: 1750815461 Timestamp [UCT]: 2025-06-25 01:37:41 Age [y:d:h:m:s]: 00:148:06:45:00
Block: 1312203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103911 RingCT/type: yes/0
Extra: 01e4adb511f4e23773811307db2a5660c07ed709c88d7ddcbee5c04a65130f347b021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4558154a83b757f784a7070b0d6c819ec3f910690879444f9c81233bb601dfc8 0.600000000000 1799834 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": 1312213, "vin": [ { "gen": { "height": 1312203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4558154a83b757f784a7070b0d6c819ec3f910690879444f9c81233bb601dfc8" } } ], "extra": [ 1, 228, 173, 181, 17, 244, 226, 55, 115, 129, 19, 7, 219, 42, 86, 96, 192, 126, 215, 9, 200, 141, 125, 220, 190, 229, 192, 74, 101, 19, 15, 52, 123, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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