Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8894ddeeb52a92afb6084409d330275f6b85de60cfb49b827f4ad3a188294685

Tx prefix hash: a2f45d948f63f2e09201b48bd6e81c2240ca81a47d89d6503e2a982e6abf180f
Tx public key: 4a1b3a2f706bbed4a1aff59d1bf6157328c025be8345eebe5475e4233a87fc60
Timestamp: 1709363158 Timestamp [UCT]: 2024-03-02 07:05:58 Age [y:d:h:m:s]: 01:110:14:09:32
Block: 969375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339932 RingCT/type: yes/0
Extra: 014a1b3a2f706bbed4a1aff59d1bf6157328c025be8345eebe5475e4233a87fc600211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfbed75819216dced2c1ecf9ca69d7ba0d2b3b746d08e763f1ba5bbe4178241c 0.600000000000 1429204 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": 969385, "vin": [ { "gen": { "height": 969375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfbed75819216dced2c1ecf9ca69d7ba0d2b3b746d08e763f1ba5bbe4178241c" } } ], "extra": [ 1, 74, 27, 58, 47, 112, 107, 190, 212, 161, 175, 245, 157, 27, 246, 21, 115, 40, 192, 37, 190, 131, 69, 238, 190, 84, 117, 228, 35, 58, 135, 252, 96, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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