Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a116a6404f3372e54b8c0087384c624af7be54e6f72f1b6d5d392b7150eec8

Tx prefix hash: 17019bd84b2562f46a06f6caca576952e44a62278e50ebc57316b3204a7b24a5
Tx public key: 69a51b2d4f22643ec6356aa0ec69397da68efc7e1c1d6139f2e9fd8c7b84e619
Timestamp: 1763506602 Timestamp [UCT]: 2025-11-18 22:56:42 Age [y:d:h:m:s]: 00:048:00:03:41
Block: 1415115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34396 RingCT/type: yes/0
Extra: 0169a51b2d4f22643ec6356aa0ec69397da68efc7e1c1d6139f2e9fd8c7b84e619021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85891684f3570c5fb6bbc5756e5ec31bfb4fbe448e7c84c106f46d88aabf1202 0.600000000000 1903610 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": 1415125, "vin": [ { "gen": { "height": 1415115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85891684f3570c5fb6bbc5756e5ec31bfb4fbe448e7c84c106f46d88aabf1202" } } ], "extra": [ 1, 105, 165, 27, 45, 79, 34, 100, 62, 198, 53, 106, 160, 236, 105, 57, 125, 166, 142, 252, 126, 28, 29, 97, 57, 242, 233, 253, 140, 123, 132, 230, 25, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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