Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa66d3f35f9fcac9af31e8a037218f972bbfbb98dd77a37da7dfda2528403c73

Tx prefix hash: 77bcd424c8ba0c143003f77fd2b3793b61f6dc542a2d70c35c4869b1bee5b869
Tx public key: 2aac35de3efb8f7af4ac76729bd4a0f7ca8e7ac42f2f692d3628dfffed5f0fda
Timestamp: 1719964644 Timestamp [UCT]: 2024-07-02 23:57:24 Age [y:d:h:m:s]: 00:324:19:27:49
Block: 1057249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232136 RingCT/type: yes/0
Extra: 012aac35de3efb8f7af4ac76729bd4a0f7ca8e7ac42f2f692d3628dfffed5f0fda0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2d5b9878b30a2bf81cce4fcfc4df5d602689dbd37ab644a22b4e9b721139171 0.600000000000 1527682 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": 1057259, "vin": [ { "gen": { "height": 1057249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2d5b9878b30a2bf81cce4fcfc4df5d602689dbd37ab644a22b4e9b721139171" } } ], "extra": [ 1, 42, 172, 53, 222, 62, 251, 143, 122, 244, 172, 118, 114, 155, 212, 160, 247, 202, 142, 122, 196, 47, 47, 105, 45, 54, 40, 223, 255, 237, 95, 15, 218, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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