Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 365bf3b4aac11d7f62a1fca3f36cba02e4ec2a20a660c92491381f6eb80af2b0

Tx prefix hash: 8f994a53b637e5a6ea708472e412bcecee8b1fa4fccea8468109c08d18ecf775
Tx public key: 059a72b5c4980824ffc228db2d48fd90c9dfe4e5b9ae3a2c288d75722f7f9ce5
Timestamp: 1751470116 Timestamp [UCT]: 2025-07-02 15:28:36 Age [y:d:h:m:s]: 00:142:07:43:39
Block: 1317299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99969 RingCT/type: yes/0
Extra: 01059a72b5c4980824ffc228db2d48fd90c9dfe4e5b9ae3a2c288d75722f7f9ce5021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ae957e23584562c218c9958e9fad6c1f892d7a8e33032bc0f836ffa6cfb12cf 0.600000000000 1804966 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": 1317309, "vin": [ { "gen": { "height": 1317299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ae957e23584562c218c9958e9fad6c1f892d7a8e33032bc0f836ffa6cfb12cf" } } ], "extra": [ 1, 5, 154, 114, 181, 196, 152, 8, 36, 255, 194, 40, 219, 45, 72, 253, 144, 201, 223, 228, 229, 185, 174, 58, 44, 40, 141, 117, 114, 47, 127, 156, 229, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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