Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44d0a346991378c025dbdc0efa41a00d533447a0f2867aed772d51fe4888cae6

Tx prefix hash: 62771a53675d8a0332370319df68cef0c5d1985746d980f11da3f7f2a0a96501
Tx public key: 2f541d040be1217bef20c14bbe6eae819cad5fc3609ea132f3a10eb31e73eecc
Timestamp: 1700481229 Timestamp [UCT]: 2023-11-20 11:53:49 Age [y:d:h:m:s]: 01:143:20:15:00
Block: 895739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363979 RingCT/type: yes/0
Extra: 012f541d040be1217bef20c14bbe6eae819cad5fc3609ea132f3a10eb31e73eecc02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.660761672000 dcy

stealth address amount amount idx
00: ce3d1ad73d105b4c40807b97a3cd8a08c45cbb775780afb7c94fc64cb5ef028b 0.660761672000 1351986 of 0

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": 895749, "vin": [ { "gen": { "height": 895739 } } ], "vout": [ { "amount": 660761672, "target": { "key": "ce3d1ad73d105b4c40807b97a3cd8a08c45cbb775780afb7c94fc64cb5ef028b" } } ], "extra": [ 1, 47, 84, 29, 4, 11, 225, 33, 123, 239, 32, 193, 75, 190, 110, 174, 129, 156, 173, 95, 195, 96, 158, 161, 50, 243, 161, 14, 179, 30, 115, 238, 204, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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