Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66a302fe6f4e2a2197c66fd37d48fd4613e8474c68c8350c5d2185118c5eadd3

Tx prefix hash: 38e1f268c432ae83ece9658e23251e000d3181b5ca1d76ce98eed8387cb3a3a2
Tx public key: 69fa6d8a39468d24ebd706e8c8fa54f2e91d622178659ce7daee719318c749e0
Timestamp: 1712729903 Timestamp [UCT]: 2024-04-10 06:18:23 Age [y:d:h:m:s]: 01:035:22:50:44
Block: 997259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286675 RingCT/type: yes/0
Extra: 0169fa6d8a39468d24ebd706e8c8fa54f2e91d622178659ce7daee719318c749e002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51f90d4c4e339f2438b0478cc3af028a5a3d9126409352f361a6e162030b9121 0.600000000000 1457689 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": 997269, "vin": [ { "gen": { "height": 997259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51f90d4c4e339f2438b0478cc3af028a5a3d9126409352f361a6e162030b9121" } } ], "extra": [ 1, 105, 250, 109, 138, 57, 70, 141, 36, 235, 215, 6, 232, 200, 250, 84, 242, 233, 29, 98, 33, 120, 101, 156, 231, 218, 238, 113, 147, 24, 199, 73, 224, 2, 17, 0, 0, 0, 1, 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