Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 716d6c785949f2d07476643fbe9a0fecc9622f327221c9bfbfac351e1d8f6ce5

Tx prefix hash: 684ed4b82b8b2dd8e58ee24dfd7eb8be63810ca58bd65b14a17aa84c8bed31f4
Tx public key: 69e6e6f57b27a0758c107ca02c410acbb13ffc5d356085c2a3e73e7fddfc2da8
Timestamp: 1581640213 Timestamp [UCT]: 2020-02-14 00:30:13 Age [y:d:h:m:s]: 04:321:23:00:53
Block: 64502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122261 RingCT/type: yes/0
Extra: 0169e6e6f57b27a0758c107ca02c410acbb13ffc5d356085c2a3e73e7fddfc2da8021100000002c71d3ff9000000000000000000

1 output(s) for total of 375.213892228000 dcy

stealth address amount amount idx
00: 9b8334783e362d2bf3ea267492a2c4e14f054c7ff36178fd70a0aa096f1d80fb 375.213892228000 118981 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": 64512, "vin": [ { "gen": { "height": 64502 } } ], "vout": [ { "amount": 375213892228, "target": { "key": "9b8334783e362d2bf3ea267492a2c4e14f054c7ff36178fd70a0aa096f1d80fb" } } ], "extra": [ 1, 105, 230, 230, 245, 123, 39, 160, 117, 140, 16, 124, 160, 44, 65, 10, 203, 177, 63, 252, 93, 53, 96, 133, 194, 163, 231, 62, 127, 221, 252, 45, 168, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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