Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b2acf9c57b77669a15eb511a3074d7c9eba0fda4cb82017394f99bff06df4df

Tx prefix hash: 7635de38d2be8a95ced97a3607a5ca56842e67922da16e1391750c27da03c3ac
Tx public key: 52541d8c77a6e9424b680ceb3b32c95bec9cff289f751f5be542d12cac2ed03c
Timestamp: 1722682700 Timestamp [UCT]: 2024-08-03 10:58:20 Age [y:d:h:m:s]: 00:347:17:23:38
Block: 1079792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247378 RingCT/type: yes/0
Extra: 0152541d8c77a6e9424b680ceb3b32c95bec9cff289f751f5be542d12cac2ed03c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c7a290b6486015b4f282a67ed9d6f6434f559e7d597e44e801fd8f7916ecdb2 0.600000000000 1552901 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": 1079802, "vin": [ { "gen": { "height": 1079792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c7a290b6486015b4f282a67ed9d6f6434f559e7d597e44e801fd8f7916ecdb2" } } ], "extra": [ 1, 82, 84, 29, 140, 119, 166, 233, 66, 75, 104, 12, 235, 59, 50, 201, 91, 236, 156, 255, 40, 159, 117, 31, 91, 229, 66, 209, 44, 172, 46, 208, 60, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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