Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9bfd937afdc96c4ef9a35bdc1ad0f832ab0601e79091ae68eb7afeabb091f8

Tx prefix hash: 2502a94f30c9623d1bb233af64aa8ac32510a3e426e960e32c6723cd627afe43
Tx public key: c1a724c4ea91e301a391880da7439c61f37fdaa3d42b0e14400efb9dd9faf338
Timestamp: 1764304207 Timestamp [UCT]: 2025-11-28 04:30:07 Age [y:d:h:m:s]: 00:025:13:27:37
Block: 1421730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18297 RingCT/type: yes/0
Extra: 01c1a724c4ea91e301a391880da7439c61f37fdaa3d42b0e14400efb9dd9faf338021100000004da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a1db3e4b5c86a8e915105fe250c7132526890de72c8c79fb534af3772bc05f1 0.600000000000 1910287 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": 1421740, "vin": [ { "gen": { "height": 1421730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a1db3e4b5c86a8e915105fe250c7132526890de72c8c79fb534af3772bc05f1" } } ], "extra": [ 1, 193, 167, 36, 196, 234, 145, 227, 1, 163, 145, 136, 13, 167, 67, 156, 97, 243, 127, 218, 163, 212, 43, 14, 20, 64, 14, 251, 157, 217, 250, 243, 56, 2, 17, 0, 0, 0, 4, 218, 85, 72, 72, 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