Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3713e36c8cb26bd66dc1e23542eaf8dbe563769064d957882de4ab5123109d0d

Tx prefix hash: d4f5b5e19cb24f3f8bb024b62f08505a7d2119f970a7be5ee53b9b95d40ee96e
Tx public key: 210ca8cf380e9c99358dc501b5d89e9ad31d56eafe528037f3ec22c7f9ef16e6
Timestamp: 1711673319 Timestamp [UCT]: 2024-03-29 00:48:39 Age [y:d:h:m:s]: 00:248:19:43:33
Block: 988542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178122 RingCT/type: yes/0
Extra: 01210ca8cf380e9c99358dc501b5d89e9ad31d56eafe528037f3ec22c7f9ef16e6021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51b6c2428ca39d7110a857755bd85426aad9a39f9ceb412900600263867e70fc 0.600000000000 1448821 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": 988552, "vin": [ { "gen": { "height": 988542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51b6c2428ca39d7110a857755bd85426aad9a39f9ceb412900600263867e70fc" } } ], "extra": [ 1, 33, 12, 168, 207, 56, 14, 156, 153, 53, 141, 197, 1, 181, 216, 158, 154, 211, 29, 86, 234, 254, 82, 128, 55, 243, 236, 34, 199, 249, 239, 22, 230, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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