Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0afa32e6493f3178744c0f71a1138e5928e76f02be9b5145229071e7e460049b

Tx prefix hash: d86fba184ee2b4e0ebaf07035db5743298294eb7cb085f7c8a729689dc16081b
Tx public key: 7df8d5a2b7384578bf927c6623932735839ddb5297816c852ca8b3832b08fbf0
Timestamp: 1716775584 Timestamp [UCT]: 2024-05-27 02:06:24 Age [y:d:h:m:s]: 00:308:13:58:52
Block: 1030830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220535 RingCT/type: yes/0
Extra: 017df8d5a2b7384578bf927c6623932735839ddb5297816c852ca8b3832b08fbf002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7caa9e593fffa046a4d2bd0a2438d6ecd7c8830974e384a75ea4fa0b8616f33 0.600000000000 1499131 of 15

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": 1030840, "vin": [ { "gen": { "height": 1030830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7caa9e593fffa046a4d2bd0a2438d6ecd7c8830974e384a75ea4fa0b8616f33" } } ], "extra": [ 1, 125, 248, 213, 162, 183, 56, 69, 120, 191, 146, 124, 102, 35, 147, 39, 53, 131, 157, 219, 82, 151, 129, 108, 133, 44, 168, 179, 131, 43, 8, 251, 240, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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