Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9ac8902677f6832d514cd2ad0a019cc8eca0125e81f895ce33969dd0861cbd0

Tx prefix hash: 9af6f4fed56579289a1f1e2eab7d8baca1cf2eb47b6a4fabc9fb8472bb27ec45
Tx public key: aa862a002b4f72517cbfcf17422cb5e471ad4a0438c36b867cb6c179ac7e0379
Timestamp: 1747626375 Timestamp [UCT]: 2025-05-19 03:46:15 Age [y:d:h:m:s]: 00:142:01:34:06
Block: 1286045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99175 RingCT/type: yes/0
Extra: 01aa862a002b4f72517cbfcf17422cb5e471ad4a0438c36b867cb6c179ac7e03790211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b15ba2a3876b8c40149d954a11fb5fb01c8d3aa914701ea02c5f851768f76ea 0.600000000000 1773510 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": 1286055, "vin": [ { "gen": { "height": 1286045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b15ba2a3876b8c40149d954a11fb5fb01c8d3aa914701ea02c5f851768f76ea" } } ], "extra": [ 1, 170, 134, 42, 0, 43, 79, 114, 81, 124, 191, 207, 23, 66, 44, 181, 228, 113, 173, 74, 4, 56, 195, 107, 134, 124, 182, 193, 121, 172, 126, 3, 121, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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