Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1564b0691b447c1fa9ef500f180b2062f974f2860f67af4f562acb389196676

Tx prefix hash: 2bf6476423f7c874203c58c8f133ce46194e55ffb6f5a74de8b017f267a5bbcb
Tx public key: a7043efbdcf6c6c0986d6f84efe8891b82a821bcca813d6d0c1268efaf01e576
Timestamp: 1716762245 Timestamp [UCT]: 2024-05-26 22:24:05 Age [y:d:h:m:s]: 00:311:15:57:29
Block: 1030723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222738 RingCT/type: yes/0
Extra: 01a7043efbdcf6c6c0986d6f84efe8891b82a821bcca813d6d0c1268efaf01e576021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a45e23c3975447b908bf26559ee167fa12c0ed6576982e7e963f07abd560f266 0.600000000000 1498996 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": 1030733, "vin": [ { "gen": { "height": 1030723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a45e23c3975447b908bf26559ee167fa12c0ed6576982e7e963f07abd560f266" } } ], "extra": [ 1, 167, 4, 62, 251, 220, 246, 198, 192, 152, 109, 111, 132, 239, 232, 137, 27, 130, 168, 33, 188, 202, 129, 61, 109, 12, 18, 104, 239, 175, 1, 229, 118, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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