Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87015a48571bfca3d25c344056b6acb8f010e52cba2e3f70656095aeecb6be2f

Tx prefix hash: b6dace66e1d7401d372005f153a5a4ea5bc79d56d5a99dfa1e529211e08188ea
Tx public key: d0483d0ae04dad7962036e2705cd3a656f0c75049842b2664a348e463de28a99
Timestamp: 1583540639 Timestamp [UCT]: 2020-03-07 00:23:59 Age [y:d:h:m:s]: 05:053:13:17:33
Block: 78029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193305 RingCT/type: yes/0
Extra: 01d0483d0ae04dad7962036e2705cd3a656f0c75049842b2664a348e463de28a99021100000003a33b4a85000000000000000000

1 output(s) for total of 338.421794849000 dcy

stealth address amount amount idx
00: f7fe0b921d70c0980600f1a808c27f02b22ea78cad8b168903952bd8148f6187 338.421794849000 143286 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": 78039, "vin": [ { "gen": { "height": 78029 } } ], "vout": [ { "amount": 338421794849, "target": { "key": "f7fe0b921d70c0980600f1a808c27f02b22ea78cad8b168903952bd8148f6187" } } ], "extra": [ 1, 208, 72, 61, 10, 224, 77, 173, 121, 98, 3, 110, 39, 5, 205, 58, 101, 111, 12, 117, 4, 152, 66, 178, 102, 74, 52, 142, 70, 61, 226, 138, 153, 2, 17, 0, 0, 0, 3, 163, 59, 74, 133, 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