Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65b0b20c28bb8d0d2f446ca5f5b953b964dd76e2ac17b7c2e1824dee102be648

Tx prefix hash: 3d49d7068f7b87b449787be74ddecaa138376a580c95d431f4d59cd31e0e33f7
Tx public key: bff169232cbd66e84412cb079e604253ca6ca64d4fbf3151c06644d9b69f603d
Timestamp: 1705421967 Timestamp [UCT]: 2024-01-16 16:19:27 Age [y:d:h:m:s]: 01:066:17:07:14
Block: 936676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308780 RingCT/type: yes/0
Extra: 01bff169232cbd66e84412cb079e604253ca6ca64d4fbf3151c06644d9b69f603d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e88e51e4b3ad13ca7c42baa2ca6cedff071c291fc2a5fc8e9312a3a32df04b1e 0.600000000000 1394714 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": 936686, "vin": [ { "gen": { "height": 936676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e88e51e4b3ad13ca7c42baa2ca6cedff071c291fc2a5fc8e9312a3a32df04b1e" } } ], "extra": [ 1, 191, 241, 105, 35, 44, 189, 102, 232, 68, 18, 203, 7, 158, 96, 66, 83, 202, 108, 166, 77, 79, 191, 49, 81, 192, 102, 68, 217, 182, 159, 96, 61, 2, 17, 0, 0, 0, 4, 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