Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5011b6e8207b55181a41b98e399a76d33f42f61559bc7a40c6a4f7f42f27282

Tx prefix hash: dd08f4918b6c74e6c848623edcfb103e950d4de196e21db73a12eaa913a53d94
Tx public key: 4ed2ad1c5a49af3cff4e0c49b501b274e60245dff125e3f48ebff2d769d0b731
Timestamp: 1708454790 Timestamp [UCT]: 2024-02-20 18:46:30 Age [y:d:h:m:s]: 01:033:20:16:41
Block: 961841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285200 RingCT/type: yes/0
Extra: 014ed2ad1c5a49af3cff4e0c49b501b274e60245dff125e3f48ebff2d769d0b7310211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6379ac3620b872d90391e18cee763e45acdda764f06e4f967c096ff6a8936f4 0.600000000000 1421454 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": 961851, "vin": [ { "gen": { "height": 961841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6379ac3620b872d90391e18cee763e45acdda764f06e4f967c096ff6a8936f4" } } ], "extra": [ 1, 78, 210, 173, 28, 90, 73, 175, 60, 255, 78, 12, 73, 181, 1, 178, 116, 230, 2, 69, 223, 241, 37, 227, 244, 142, 191, 242, 215, 105, 208, 183, 49, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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