Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61b291d16e9fbb69bcbc6deff2911fe6ebc0bfa9de89186509f55ec77737554b

Tx prefix hash: 562e66af65731ab78613ed5c4b2639f30d5194bec4b5c1a68c69c9f70158a9c0
Tx public key: 245aa6cd778a8dcd9ef94499f023825ce04dfe13a4e5391f40cde188683af4e8
Timestamp: 1587403682 Timestamp [UCT]: 2020-04-20 17:28:02 Age [y:d:h:m:s]: 04:226:03:16:02
Block: 94601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1071347 RingCT/type: yes/0
Extra: 01245aa6cd778a8dcd9ef94499f023825ce04dfe13a4e5391f40cde188683af4e80211000000028a2ee0d9000000000000000000

1 output(s) for total of 298.233128731000 dcy

stealth address amount amount idx
00: ef7b71a6e77fd1522bd427f317f33417f4f04daebdf3f602a2465596fe0c2cf0 298.233128731000 168307 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": 94611, "vin": [ { "gen": { "height": 94601 } } ], "vout": [ { "amount": 298233128731, "target": { "key": "ef7b71a6e77fd1522bd427f317f33417f4f04daebdf3f602a2465596fe0c2cf0" } } ], "extra": [ 1, 36, 90, 166, 205, 119, 138, 141, 205, 158, 249, 68, 153, 240, 35, 130, 92, 224, 77, 254, 19, 164, 229, 57, 31, 64, 205, 225, 136, 104, 58, 244, 232, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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