Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 531d6f5080e2a0b5bdc559c6b72fc389fb5edc0b37e4e553e007ae5bb6a07633

Tx prefix hash: ed044dc4bca8d059b2db9e1324d6977572fdf6e8c14ad60f74a1a23b2dc481c4
Tx public key: 707f7dbd63edb53e6197d3e8dd981a1cbedf593d50d5b791c2c1bcd9bb86ef41
Timestamp: 1759732497 Timestamp [UCT]: 2025-10-06 06:34:57 Age [y:d:h:m:s]: 00:038:07:00:00
Block: 1383839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27421 RingCT/type: yes/0
Extra: 01707f7dbd63edb53e6197d3e8dd981a1cbedf593d50d5b791c2c1bcd9bb86ef41021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5175b7b92b85e20c4de147e2f9c3b955c5c9820fa98a52d5a93bc73e8893eb1e 0.600000000000 1871988 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": 1383849, "vin": [ { "gen": { "height": 1383839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5175b7b92b85e20c4de147e2f9c3b955c5c9820fa98a52d5a93bc73e8893eb1e" } } ], "extra": [ 1, 112, 127, 125, 189, 99, 237, 181, 62, 97, 151, 211, 232, 221, 152, 26, 28, 190, 223, 89, 61, 80, 213, 183, 145, 194, 193, 188, 217, 187, 134, 239, 65, 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