Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03d77422093db2acbf22d3b378cd127cd934b134f6661c0895f59f6e2ee13ba6

Tx prefix hash: 5fffd8d5e0663481b196e32d89f41da2d4e914f67b17b89b05c81f78a15e965e
Tx public key: 1da8a52c76a00d8e56e956593db4f5819f15bbf5d3dddf79dd6bf32d8b0aca1b
Timestamp: 1572893474 Timestamp [UCT]: 2019-11-04 18:51:14 Age [y:d:h:m:s]: 05:020:04:41:30
Block: 734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1158859 RingCT/type: yes/0
Extra: 011da8a52c76a00d8e56e956593db4f5819f15bbf5d3dddf79dd6bf32d8b0aca1b

1 output(s) for total of 610.335819079000 dcy

stealth address amount amount idx
00: d6ed64b1ec4c2e0d05cc7d7037942e0f6b5e0da60186c10bcece32674e9fe8e8 610.335819079000 690 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": 744, "vin": [ { "gen": { "height": 734 } } ], "vout": [ { "amount": 610335819079, "target": { "key": "d6ed64b1ec4c2e0d05cc7d7037942e0f6b5e0da60186c10bcece32674e9fe8e8" } } ], "extra": [ 1, 29, 168, 165, 44, 118, 160, 13, 142, 86, 233, 86, 89, 61, 180, 245, 129, 159, 21, 187, 245, 211, 221, 223, 121, 221, 107, 243, 45, 139, 10, 202, 27 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8