Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e66e9180526a372a7fd995c5829135359bf8980c8c55e63732c04c64b861fe86

Tx prefix hash: f63ffe1bb3475239a3c6e6a3273495f07d2572cee9cf530501b53d62112a06c4
Tx public key: 38ea19d5185bc2c125e70f0b655b7a9522ac5c962851d935bf0b544b9f7284db
Timestamp: 1717133914 Timestamp [UCT]: 2024-05-31 05:38:34 Age [y:d:h:m:s]: 00:306:03:41:49
Block: 1033796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218795 RingCT/type: yes/0
Extra: 0138ea19d5185bc2c125e70f0b655b7a9522ac5c962851d935bf0b544b9f7284db02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f9c3c7187d530fedb624bfc6b8ad88a2e45763ff44e5a67cde61aa142b0d3f5 0.600000000000 1502269 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": 1033806, "vin": [ { "gen": { "height": 1033796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f9c3c7187d530fedb624bfc6b8ad88a2e45763ff44e5a67cde61aa142b0d3f5" } } ], "extra": [ 1, 56, 234, 25, 213, 24, 91, 194, 193, 37, 231, 15, 11, 101, 91, 122, 149, 34, 172, 92, 150, 40, 81, 217, 53, 191, 11, 84, 75, 159, 114, 132, 219, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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