Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e3339979a33d2c39f4a1e7cc8eec5c2469b7c3eac669a086fcb4ede08e41add

Tx prefix hash: f10eba0b9dbd34db4b5201a3850949cb90b4d64878d828b8ddfebf6bea4ffb36
Tx public key: e5c8f7c5c143c6711fd3ba0049432a12644310c9d48a90b62afa76fdcb99888c
Timestamp: 1761557297 Timestamp [UCT]: 2025-10-27 09:28:17 Age [y:d:h:m:s]: 00:071:18:54:32
Block: 1398977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51386 RingCT/type: yes/0
Extra: 01e5c8f7c5c143c6711fd3ba0049432a12644310c9d48a90b62afa76fdcb99888c02110000000525a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4bf8cf2b69ac24eda583bb01dd0c6ab61b361724aa879d6b1833f160c374232 0.600000000000 1887280 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": 1398987, "vin": [ { "gen": { "height": 1398977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4bf8cf2b69ac24eda583bb01dd0c6ab61b361724aa879d6b1833f160c374232" } } ], "extra": [ 1, 229, 200, 247, 197, 193, 67, 198, 113, 31, 211, 186, 0, 73, 67, 42, 18, 100, 67, 16, 201, 212, 138, 144, 182, 42, 250, 118, 253, 203, 153, 136, 140, 2, 17, 0, 0, 0, 5, 37, 163, 90, 15, 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