Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00f0afcd047ea0ca695270b9d8f9d6da3396b3f255fcee7851fe0d40ebada4df

Tx prefix hash: f6f681fcf9f17fa77af5954550666b0a7611abdc2713aee06b7e9e91b5781db9
Tx public key: ad8db2ad177a3ed39dff9aec7db284aa6a0012aba24f72c6beac70a76db0c804
Timestamp: 1748357530 Timestamp [UCT]: 2025-05-27 14:52:10 Age [y:d:h:m:s]: 00:172:07:14:09
Block: 1292114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120834 RingCT/type: yes/0
Extra: 01ad8db2ad177a3ed39dff9aec7db284aa6a0012aba24f72c6beac70a76db0c804021100000002523560da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41f8db0e2d7acde51668cde9a4ec26dcdb6c4aa49ef314ab06e42e0101bf44ab 0.600000000000 1779585 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": 1292124, "vin": [ { "gen": { "height": 1292114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41f8db0e2d7acde51668cde9a4ec26dcdb6c4aa49ef314ab06e42e0101bf44ab" } } ], "extra": [ 1, 173, 141, 178, 173, 23, 122, 62, 211, 157, 255, 154, 236, 125, 178, 132, 170, 106, 0, 18, 171, 162, 79, 114, 198, 190, 172, 112, 167, 109, 176, 200, 4, 2, 17, 0, 0, 0, 2, 82, 53, 96, 218, 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