Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa6c3a35d1b50a969879f2fb5dd6e06c64bd9df74ce66744b25e3d613e3f01fb

Tx prefix hash: 065efe991927727200b636517d493205a78387fca1ee5167d0d36920e1c9aa59
Tx public key: edf1f9c900a002f0e17618728b887651fcc4a01d04f193d7dba5b47659c8de85
Timestamp: 1708405744 Timestamp [UCT]: 2024-02-20 05:09:04 Age [y:d:h:m:s]: 01:262:11:12:58
Block: 961431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446333 RingCT/type: yes/0
Extra: 01edf1f9c900a002f0e17618728b887651fcc4a01d04f193d7dba5b47659c8de8502110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f51b7b3c9df449f9d9dd61f25aecf4f26b03e107e609c2fe224bd98de8719a23 0.600000000000 1421040 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": 961441, "vin": [ { "gen": { "height": 961431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f51b7b3c9df449f9d9dd61f25aecf4f26b03e107e609c2fe224bd98de8719a23" } } ], "extra": [ 1, 237, 241, 249, 201, 0, 160, 2, 240, 225, 118, 24, 114, 139, 136, 118, 81, 252, 196, 160, 29, 4, 241, 147, 215, 219, 165, 180, 118, 89, 200, 222, 133, 2, 17, 0, 0, 0, 6, 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