Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5f71e1987ad71189c44d2910f26da45b480059c5cca0b1c0f2ac856bacf5b13

Tx prefix hash: 5bffcd738852652fbd0dbdec38d8feec0f2a173e981ba0d16d18e8e0c4f59cff
Tx public key: 3524867306b0d1db1b26584c826ae5d6d1bc0dd6cfc81389cc63a4033c3e1dce
Timestamp: 1732525786 Timestamp [UCT]: 2024-11-25 09:09:46 Age [y:d:h:m:s]: 00:128:19:32:28
Block: 1161303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91868 RingCT/type: yes/0
Extra: 013524867306b0d1db1b26584c826ae5d6d1bc0dd6cfc81389cc63a4033c3e1dce0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b03276de20eb49975ac2aca66a73e9ab8c9226b8de6d19448d700f017f19b00 0.600000000000 1646954 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": 1161313, "vin": [ { "gen": { "height": 1161303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b03276de20eb49975ac2aca66a73e9ab8c9226b8de6d19448d700f017f19b00" } } ], "extra": [ 1, 53, 36, 134, 115, 6, 176, 209, 219, 27, 38, 88, 76, 130, 106, 229, 214, 209, 188, 13, 214, 207, 200, 19, 137, 204, 99, 164, 3, 60, 62, 29, 206, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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