Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3771a5e0477b4273c887a412853fa47d4c2c1a8d00f3bd6218a83a55f013906c

Tx prefix hash: 88e4f6ad7e87870d0b35316c797bb5f9f303e70c5ffbf5e7135be08f012c7e3a
Tx public key: fd44563505b7a4b2124b898c0be58b9ab00edc3e40dad844c45fae518f239cd5
Timestamp: 1634907129 Timestamp [UCT]: 2021-10-22 12:52:09 Age [y:d:h:m:s]: 03:069:07:30:04
Block: 358125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 827821 RingCT/type: yes/0
Extra: 01fd44563505b7a4b2124b898c0be58b9ab00edc3e40dad844c45fae518f239cd502110000000236fe6557000000000000000000

1 output(s) for total of 39.937752561000 dcy

stealth address amount amount idx
00: 2f60f728c035790cd32d4d214ac35718e0e2ad4b60aa1bd92a0ecea7be978f16 39.937752561000 729872 of 0

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": 358135, "vin": [ { "gen": { "height": 358125 } } ], "vout": [ { "amount": 39937752561, "target": { "key": "2f60f728c035790cd32d4d214ac35718e0e2ad4b60aa1bd92a0ecea7be978f16" } } ], "extra": [ 1, 253, 68, 86, 53, 5, 183, 164, 178, 18, 75, 137, 140, 11, 229, 139, 154, 176, 14, 220, 62, 64, 218, 216, 68, 196, 95, 174, 81, 143, 35, 156, 213, 2, 17, 0, 0, 0, 2, 54, 254, 101, 87, 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