Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b25713805454c85cb690e987e2b53e758cc75424d84fc02d4c5df0d0389addde

Tx prefix hash: 54ee5da8f4dcc6b5f3e2415f9e61561c87ac4dd4b275fd9a91197438233eb708
Tx public key: 2f285bf85ab901a7a69b7ca97d4b062ff70ea81d5e0e90f8ad5f36757eb1d58c
Timestamp: 1742086725 Timestamp [UCT]: 2025-03-16 00:58:45 Age [y:d:h:m:s]: 00:249:07:20:18
Block: 1240208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175906 RingCT/type: yes/0
Extra: 012f285bf85ab901a7a69b7ca97d4b062ff70ea81d5e0e90f8ad5f36757eb1d58c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0260e3aa33146fafd71235fbb174dd9830df8033d38395db5ae3ce57c08f910e 0.600000000000 1727173 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": 1240218, "vin": [ { "gen": { "height": 1240208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0260e3aa33146fafd71235fbb174dd9830df8033d38395db5ae3ce57c08f910e" } } ], "extra": [ 1, 47, 40, 91, 248, 90, 185, 1, 167, 166, 155, 124, 169, 125, 75, 6, 47, 247, 14, 168, 29, 94, 14, 144, 248, 173, 95, 54, 117, 126, 177, 213, 140, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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