Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fd2889b5b9eff4deb1718059704c28e8381fd9e6d1f3ae125eb828627e7e845

Tx prefix hash: 93194b7375b292504d5eded77e168f37ea587baa119af3d173f32b1e2174fa8e
Tx public key: fb59354871e1a7709a214b32bcec5b3d35cc607a2bd3ddd175a69cf5c1ca2154
Timestamp: 1705581124 Timestamp [UCT]: 2024-01-18 12:32:04 Age [y:d:h:m:s]: 01:153:08:09:25
Block: 938003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370589 RingCT/type: yes/0
Extra: 01fb59354871e1a7709a214b32bcec5b3d35cc607a2bd3ddd175a69cf5c1ca215402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfb065fbd5d4302dfc1f4fff6073024c0e0308ff316e2780bed4f8a584310bd0 0.600000000000 1396067 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": 938013, "vin": [ { "gen": { "height": 938003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfb065fbd5d4302dfc1f4fff6073024c0e0308ff316e2780bed4f8a584310bd0" } } ], "extra": [ 1, 251, 89, 53, 72, 113, 225, 167, 112, 154, 33, 75, 50, 188, 236, 91, 61, 53, 204, 96, 122, 43, 211, 221, 209, 117, 166, 156, 245, 193, 202, 33, 84, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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