Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ce13fbeace80b1af09776ca68797cf67d3127d68c85b62f646e08b8b111fd4b

Tx prefix hash: 041e7002b6b100df25a66359014c2e49f99b8857f7c5e3645ae470c3a92ca0aa
Tx public key: eebf88ac32b341fb8d3a3f9018d5c1aad2ea3c7f3e70fe0acdbeaee9ee6e3eb9
Timestamp: 1751236297 Timestamp [UCT]: 2025-06-29 22:31:37 Age [y:d:h:m:s]: 00:144:03:12:09
Block: 1315437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101184 RingCT/type: yes/0
Extra: 01eebf88ac32b341fb8d3a3f9018d5c1aad2ea3c7f3e70fe0acdbeaee9ee6e3eb902110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89398a141a4c7d4791c31b18b53368ea143f4e2467e00a9eb71518529a4b4d1a 0.600000000000 1803092 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": 1315447, "vin": [ { "gen": { "height": 1315437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89398a141a4c7d4791c31b18b53368ea143f4e2467e00a9eb71518529a4b4d1a" } } ], "extra": [ 1, 238, 191, 136, 172, 50, 179, 65, 251, 141, 58, 63, 144, 24, 213, 193, 170, 210, 234, 60, 127, 62, 112, 254, 10, 205, 190, 174, 233, 238, 110, 62, 185, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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