Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59ec3ce7b2ecef47eb4569c1db4757576a46b04bb17c01574a748dde2b3d2f67

Tx prefix hash: 6015d1480d6681cad088a333334c72e54c72a3946e909b69b3ac12c588813f4b
Tx public key: f7c7bd458b62183af658278309d0f74f5b5ee4a8d2937cf5f28679e8f105e56d
Timestamp: 1615695514 Timestamp [UCT]: 2021-03-14 04:18:34 Age [y:d:h:m:s]: 03:328:19:35:34
Block: 218095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 994161 RingCT/type: yes/0
Extra: 01f7c7bd458b62183af658278309d0f74f5b5ee4a8d2937cf5f28679e8f105e56d0211000001dba9e81d35000000000000000000

1 output(s) for total of 116.241532764000 dcy

stealth address amount amount idx
00: 1a769d09ae1b3eddcfbe43c5e2cfe1fd0ccdf4d4989af7b024e5387c53f6aa31 116.241532764000 448015 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": 218105, "vin": [ { "gen": { "height": 218095 } } ], "vout": [ { "amount": 116241532764, "target": { "key": "1a769d09ae1b3eddcfbe43c5e2cfe1fd0ccdf4d4989af7b024e5387c53f6aa31" } } ], "extra": [ 1, 247, 199, 189, 69, 139, 98, 24, 58, 246, 88, 39, 131, 9, 208, 247, 79, 91, 94, 228, 168, 210, 147, 124, 245, 242, 134, 121, 232, 241, 5, 229, 109, 2, 17, 0, 0, 1, 219, 169, 232, 29, 53, 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