Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed6abd9dc678b65951e88f1c81c41b61f4a2c466bca6c05180bacbe001268842

Tx prefix hash: b5dbcc8baf0da765dbc888fcc79e2bc4e8cb211a796b5b76b811e5cd38c42e9e
Tx public key: d98fe37e4da4c88cd5470f46831f8edecb06da36a92cde382fb5fa1b090f6ce6
Timestamp: 1583636806 Timestamp [UCT]: 2020-03-08 03:06:46 Age [y:d:h:m:s]: 05:068:09:43:06
Block: 78412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1204346 RingCT/type: yes/0
Extra: 01d98fe37e4da4c88cd5470f46831f8edecb06da36a92cde382fb5fa1b090f6ce6021100000007a33b4a85000000000000000000

1 output(s) for total of 337.434346327000 dcy

stealth address amount amount idx
00: acb8d8a67dfb2f6e66d2e0aed5b0bafb44befffa8ac0b6ddfcce08c0a56ecff3 337.434346327000 143862 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": 78422, "vin": [ { "gen": { "height": 78412 } } ], "vout": [ { "amount": 337434346327, "target": { "key": "acb8d8a67dfb2f6e66d2e0aed5b0bafb44befffa8ac0b6ddfcce08c0a56ecff3" } } ], "extra": [ 1, 217, 143, 227, 126, 77, 164, 200, 140, 213, 71, 15, 70, 131, 31, 142, 222, 203, 6, 218, 54, 169, 44, 222, 56, 47, 181, 250, 27, 9, 15, 108, 230, 2, 17, 0, 0, 0, 7, 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