Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f28ed8ac94eed3d5d6d869f3a43b00c35013994da0eb5664fbdf5d5f966fea99

Tx prefix hash: c4426f09f0b945511613447b5915fb6d4c6c1ac80ee245c386f7a7bcd1227eb9
Tx public key: 5aa4196aa586f90c1ece53d2f4caa895e44e12356674e1427bb2af495386f6b8
Timestamp: 1716418624 Timestamp [UCT]: 2024-05-22 22:57:04 Age [y:d:h:m:s]: 00:245:20:01:53
Block: 1027868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175893 RingCT/type: yes/0
Extra: 015aa4196aa586f90c1ece53d2f4caa895e44e12356674e1427bb2af495386f6b80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d582c9acbe24571fe723cbe3e9a6cad84f067e8830a25a1c9e1b4a992a6ec40b 0.600000000000 1495727 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": 1027878, "vin": [ { "gen": { "height": 1027868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d582c9acbe24571fe723cbe3e9a6cad84f067e8830a25a1c9e1b4a992a6ec40b" } } ], "extra": [ 1, 90, 164, 25, 106, 165, 134, 249, 12, 30, 206, 83, 210, 244, 202, 168, 149, 228, 78, 18, 53, 102, 116, 225, 66, 123, 178, 175, 73, 83, 134, 246, 184, 2, 17, 0, 0, 0, 1, 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