Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57156f2bf39fc3f4ca258ad50f532ca8ac6d295901dc6e7433e0b1c2a98e0a37

Tx prefix hash: 53b75482d0cdd5c673f3808655d5f95a197159339ff065fbd56921bbfd8a50b3
Tx public key: ec98a528292fef951d656f1b6581eba3f0ccdc3e65495f4e03067b71db2740ba
Timestamp: 1626821897 Timestamp [UCT]: 2021-07-20 22:58:17 Age [y:d:h:m:s]: 03:161:12:07:59
Block: 297855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 887117 RingCT/type: yes/0
Extra: 01ec98a528292fef951d656f1b6581eba3f0ccdc3e65495f4e03067b71db2740ba02110000000104712537000000000000000000

1 output(s) for total of 63.253306560000 dcy

stealth address amount amount idx
00: 7e6665021a9995bdb48cf0a892d752d6e5b123d93b58358364877cc04a1b80f6 63.253306560000 623350 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": 297865, "vin": [ { "gen": { "height": 297855 } } ], "vout": [ { "amount": 63253306560, "target": { "key": "7e6665021a9995bdb48cf0a892d752d6e5b123d93b58358364877cc04a1b80f6" } } ], "extra": [ 1, 236, 152, 165, 40, 41, 47, 239, 149, 29, 101, 111, 27, 101, 129, 235, 163, 240, 204, 220, 62, 101, 73, 95, 78, 3, 6, 123, 113, 219, 39, 64, 186, 2, 17, 0, 0, 0, 1, 4, 113, 37, 55, 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