Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d4c5da881a27d937e2cf0d4495651f694c1b8e1f5a1e4379fb2183c3d541019

Tx prefix hash: 899aae630f7cd13405934c8993e0c0ff622816e040093b3c91eee3c88e8ff864
Tx public key: 8d535aa7ee7d7db58245c37018e7cc32f4a4da20fb68bd373adbf51c37fb8b82
Timestamp: 1708379862 Timestamp [UCT]: 2024-02-19 21:57:42 Age [y:d:h:m:s]: 00:341:03:52:42
Block: 961216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244177 RingCT/type: yes/0
Extra: 018d535aa7ee7d7db58245c37018e7cc32f4a4da20fb68bd373adbf51c37fb8b820211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51251fbfe179d64ceefffaae8d42431f1add4afd18063a5b8ad10217c08a7d17 0.600000000000 1420817 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": 961226, "vin": [ { "gen": { "height": 961216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51251fbfe179d64ceefffaae8d42431f1add4afd18063a5b8ad10217c08a7d17" } } ], "extra": [ 1, 141, 83, 90, 167, 238, 125, 125, 181, 130, 69, 195, 112, 24, 231, 204, 50, 244, 164, 218, 32, 251, 104, 189, 55, 58, 219, 245, 28, 55, 251, 139, 130, 2, 17, 0, 0, 0, 2, 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