Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b38f9d082eed3815f9718a196a4d7c301e7b6ebdabd5e8219efad3addb2ccc59

Tx prefix hash: 7ce8f4adfd0d3b4645aac84a3fd02437fabbce2f34666e8857ba16d1132e7d16
Tx public key: 4128717f0ccc6336c0cde2d51111501b1973823beea7f582d324347919d806de
Timestamp: 1741875431 Timestamp [UCT]: 2025-03-13 14:17:11 Age [y:d:h:m:s]: 00:295:20:18:33
Block: 1238459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209237 RingCT/type: yes/0
Extra: 014128717f0ccc6336c0cde2d51111501b1973823beea7f582d324347919d806de02110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 871ac231a976212c9416903349eae6acfe1ac9a25b3fa372ec534aaf128f0ae6 0.600000000000 1725418 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": 1238469, "vin": [ { "gen": { "height": 1238459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "871ac231a976212c9416903349eae6acfe1ac9a25b3fa372ec534aaf128f0ae6" } } ], "extra": [ 1, 65, 40, 113, 127, 12, 204, 99, 54, 192, 205, 226, 213, 17, 17, 80, 27, 25, 115, 130, 59, 238, 167, 245, 130, 211, 36, 52, 121, 25, 216, 6, 222, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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