Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ab6bb22f1696d56c44af01d9a55cb0ae76fb43359f257db116ccbd05f15c7d4

Tx prefix hash: 5edc22c248ce68c56320c7f83d33c5b5c89e694d2481b64330735fe98a448109
Tx public key: a853006dc849f48508fac19b2d3d6925d27388e0c736ba664b56086f0cba5c9a
Timestamp: 1581888116 Timestamp [UCT]: 2020-02-16 21:21:56 Age [y:d:h:m:s]: 05:068:02:51:21
Block: 66273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201781 RingCT/type: yes/0
Extra: 01a853006dc849f48508fac19b2d3d6925d27388e0c736ba664b56086f0cba5c9a02110000003e4943cd9f000000000000000000

1 output(s) for total of 370.178208168000 dcy

stealth address amount amount idx
00: 5097bfe3d1f068ab870e2c7a33fbe3ca462f9b964e127ec9f585be114a2262df 370.178208168000 122128 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": 66283, "vin": [ { "gen": { "height": 66273 } } ], "vout": [ { "amount": 370178208168, "target": { "key": "5097bfe3d1f068ab870e2c7a33fbe3ca462f9b964e127ec9f585be114a2262df" } } ], "extra": [ 1, 168, 83, 0, 109, 200, 73, 244, 133, 8, 250, 193, 155, 45, 61, 105, 37, 210, 115, 136, 224, 199, 54, 186, 102, 75, 86, 8, 111, 12, 186, 92, 154, 2, 17, 0, 0, 0, 62, 73, 67, 205, 159, 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